# Causes of run-time errors for the string pop-up keyboard

At run time the application logs error messages about the string pop-up keyboard to diagnostics under the circumstances listed below. These are common causes, but because of the wide variety of possible applications, other conditions not mentioned here may also cause error messages.

## String too long for Value connection

If the string pop-up keyboard is configured to accept more input characters than the Value connection tag length (using the Number of input characters option for the string input enable button), when the operator presses the Enter button:

- Nothing is written to the Value connection.
- The pop-up remains open and continues to show the invalid value in red.
- If Enter key handshaking is set up, the Enter connection is not set to 1 and the handshake timers do not begin timing.
- The application logs an error.

## Enter key handshaking in effect

If timing for Enter key handshaking from a previous pop-up entry is still in effect when the operator presses the Enter button:

- Nothing is written to the Value connection.
- The Enter connection remains set to 1 and the handshake timers continue timing.
- The application logs an error.

## Terminal resolution too small

If the terminal's resolution is too small to show the string pop-up keyboard, the application logs an error.

## See also

Use the string pop-up keyboard

How the string pop-up keyboard works at run time

Causes of run-time errors for the string input enable button

Configure the String Input Enable button